Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

found a way... it seems to work... would prefer reid looked at it. #806

Merged
merged 1 commit into from
Nov 6, 2023

Conversation

petersilva
Copy link
Contributor

@petersilva petersilva commented Nov 2, 2023

not sure I understood @reidsunderland 's worry when he looked at it. I went into the _resolve routine, which is where it looks at stuff after all the data is collected.
Only the first spot seems to be effective, but saw a second spot where I think it should apply, but doesn't... fixed both just in case. should be used by both sanity and status.

@petersilva petersilva merged commit 41c905c into development Nov 6, 2023
34 of 50 checks passed
@petersilva petersilva deleted the issue795_stopped_when_all_pids_missing branch November 6, 2023 15:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

sr3 status doesn't show when all instances are missing
1 participant